Skip to content

patches/rules_elixir: split hermetic_elixir.patch per upstream PR (part of #3744) - #6702

Merged
TrapsterDK merged 1 commit into
mainfrom
elixir-split-patch
Nov 4, 2026
Merged

TrapsterDK merged 1 commit into
mainfrom
elixir-split-patch

Conversation

@TrapsterDK

Copy link
Copy Markdown
Collaborator

Part of #3744.

Splits hermetic_elixir.patch into one patch file per upstream PR, applied in order. Concatenated they are byte-identical to the old patch (index lines aside), and they apply cleanly to the pinned RULES_ELIXIR_COMMIT in sequence.

After each upstream merge: bump the pin and delete that patch file and its repos.bzl and BUILD.bazel entries.

Checked: tools/dx check //patches/rules_elixir/... //elixir/toolchain:all passes. //elixir/tests (nested Bazel) was not run; CI runs it.

🤖 Generated with Claude Code

https://claude.ai/code/session_011u9TXHDZrfmzFQ2WT8QAKK

…rt of #3744)

The patch now matches the four upstream PRs, so each merge is a pin bump
plus deleting one patch file: elixir_app_name (bazelverse/rules_elixir#3),
elixir_app_deps (#2), warnings_as_errors (#4) and relocatable_tree (waits
on rules_erlang#18). Applied in that order; concatenated they equal the
old patch.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011u9TXHDZrfmzFQ2WT8QAKK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant